home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 1
/
Cream of the Crop 1.iso
/
WINDOWS
/
WIN_INFO.ARJ
/
MS_WIN-5.TXT
< prev
next >
Wrap
Text File
|
1992-08-13
|
15KB
|
556 lines
Windows 3.1 Setup Error Codes (S000 through S022)
INFORMATION:
The following information was obtained from Microsoft Online services.
--------------------------------------------------------------------
| INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY |
| ACCOMPANY THIS DOCUMENT (collectively referred to as an |
| Application Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY |
| KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO |
| THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A |
| PARTICULAR PURPOSE. The user assumes the entire risk as to the |
| accuracy and the use of this Application Note. This Application |
| Note may be copied and distributed subject to the following |
| conditions: 1) All text must be copied without modification and |
| all pages must be included; 2) If software is included, all files |
| on the disk(s) must be copied without modification (the DOS |
| utility DISKCOPY is appropriate for this purpose); 3) All |
| components of this Application Note must be distributed together; |
| and 4) This Application Note may not be distributed for profit. |
| |
| Copyright 1990 Microsoft Corporation. All Rights Reserved. |
| Microsoft and the Microsoft logo are registered trademarks of |
| Microsoft Corporation. |
--------------------------------------------------------------------
Summary:
When a Setup error message contains an error code, it also
includes some text indicating what Setup was trying to do,
for example, copying a file. The text of the error message
indicates whether the error is fatal or not. In some non-
fatal cases, Setup may be performing an operation (such as
copying a file) that is needed in order to run Windows.
Other times the error may prevent some specific feature of
Windows from operating properly.
In many cases, the error code is an MS-DOS extended error
code. These error codes are between 0 and 100. Setup-
specific error codes have two different formats, depending
on whether the error occurs during the character (MS-DOS)
mode or the Windows graphical user interface (GUI) mode
portion of Setup. The character mode Setup-specific error
numbers are in the format "Snnn", where "nnn" is any three
digits. The GUI mode error numbers have codes greater than
200.
In both character and GUI modes, the following MS-DOS error codes may
be reported:
02 File not found - possible corrupt disks.
03 Path not found - possible hardware problem or incompatible
software (virus?).
04 Too many open files - should never occur.
05 Access denied - make sure the file is not write protected or
protected by virus protection software.
06 Handle invalid - serious problem, unknown.
07 Memory control blocks destroyed - serious problem, unknown.
08 Insufficient memory - free up memory and run Setup again. May
also occur if very long or corrupt SYSTEM.INI, WIN.INI or
SETUP.INF files exist.
09 Memory block address invalid - serious problem, unknown.
10 Environment invalid - serious problem, unknown.
11 Format invalid - serious problem, unknown.
12 Access code invalid - serious problem, unknown.
13 Data invalid - serious problem, unknown.
14 Unknown unit - serious problem, unknown.
15 Disk drive invalid - serious problem, unknown.
16 Attempted to remove current directory - serious problem,
unknown.
17 Not same device - serious problem, unknown.
18 No more files - serious problem, unknown.
19 Write-protected disk - should never occur (different error
message).
20 Unknown unit - serious problem, unknown.
21 Drive not ready - should never occur (different error message).
22 Unknown command - serious problem, unknown.
23 Data error (CRC) - possible corrupt disks.
24 Bad request-structure length - serious problem, unknown.
25 Seek error - possible corrupt disks.
26 Unknown media type - possible corrupt disks.
27 Sector not found - possible corrupt disks.
28 Write fault - possible corrupt disks.
30 Read fault - possible corrupt disks.
31 General failure - possible corrupt disks.
32 Sharing violation - should never occur (different error message).
33 File-lock violation - should never occur (different error
message).
34 Disk change invalid - serious problem, unknown.
35 FCB unavailable - serious problem, unknown.
When setting up to or from a network, the following MS-DOS error codes
can occur:
50 Unsupported network request - serious problem, unknown.
51 Remote machine not listening - serious problem, unknown.
52 Duplicate name on network - serious problem, unknown.
53 Network name not found - serious problem, unknown.
54 Network busy - retry operation.
55 Device no longer exists on network - check with network
administrator.
56 NetBIOS command limit exceeded - check with network
administrator.
57 Error in network adapter hardware - check with network
administrator.
58 Incorrect response from network - check with network
administrator.
59 Unexpected network error - check with network administrator.
60 Remote adapter incompatible - serious problem, unknown.
64 Network name deleted - serious problem, unknown.
65 Network access denied - check with network administrator.
66 Incorrect network device type - serious problem, unknown.
67 Network name not found - serious problem, unknown.
68 Network name limit exceeded - check with network administrator.
69 NetBIOS session limit exceeded - check with network
administrator.
70 Temporary pause in file sharing - check with network
administrator.
71 Network request not accepted - check with network administrator.
72 Print or disk redirection paused - serious problem, unknown.
80 File already exists - serious problem, unknown. Setup will use
MS-DOS to make sure it can write over existing files.
82 Cannot make directory - check with network administrator.
83 Fail on Int 24H (critical error) - some drivers will fail an
access when an error occurs without issuing an Int 24H (which
causes Setup to display an error message allowing you to
retry the operation rather than just failing it). The cause of
the error is bad disks or network problems. Some viruses and
virus-protection software will sometimes cause this error to
occur.
84 Too many redirections - serious problem, unknown.
85 Duplicate redirection - serious problem, unknown.
86 Invalid password - check with network administrator.
87 Invalid parameter - serious problem, unknown.
88 Net write fault - check with network administrator.
Character Mode Setup Error Codes
--------------------------------
S001
Could not open SETUP.INF. SETUP.INF should reside on the
first Windows Setup disk for first-time installations or
upgrades and should reside in the WINDOWS\SYSTEM
subdirectory when Setup is used to change the system
configuration after Windows has been set up. If you are
changing the configuration, make sure SETUP.INF does not
exist in the WINDOWS directory and copy SETUP.INF from
the first Windows Setup disk to the WINDOWS\SYSTEM
subdirectory and try again. If it is a first-time
installation or upgrade, make sure to set the current
drive and directory to the location of the Setup program
and then run Setup from the
MS-DOS prompt.
S002
Could not load SETUP.INF. Usually due to lack of memory.
May also be due to a corrupt SETUP.INF. Should not occur
during a first-time installation or upgrade. After
making sure that there is enough memory, follow the
instructions for S001.
S004
Entry not found in SETUP.INF: [winexec].krnl386. Should
not occur during first-time installation or upgrade.
Setup has probably found an invalid SETUP.INF on the
user's system. Follow the instructions for S001.
S005
Entry not found in SETUP.INF: [winexec].krnl286. Setup
has probably found an invalid SETUP.INF on the user's
system. Follow the instructions for S001.
S006
Entry not found in SETUP.INF: [winexec].dosx. Setup has
probably found an invalid SETUP.INF on the user's
system. Follow the instructions for S001.
S007
Entry not found in SETUP.INF: [special_adapter].cdrom.
Setup has probably found an invalid SETUP.INF on the
user's system. Follow the instructions for S001.
S008
Entry not found in SETUP.INF: [winexec].exechimem. Setup
has probably found an invalid SETUP.INF on the user's
system. Follow the instructions for S001.
S009
Entry not found in SETUP.INF: [winexec].himemcmd. Setup
has probably found an invalid SETUP.INF on the user's
system. Follow the instructions for S001.
S010
Entry not found in SETUP.INF: [data].welcome. Setup has
probably found an invalid SETUP.INF on the user's
system. Follow the instructions for S001.
S012
Entry not found in SETUP.INF: [machine] <line>. Setup
has probably found an invalid SETUP.INF on the user's
system. Follow the instructions for S001.
S013
Entry not found in SETUP.INF: [machine] <line>. Setup
has probably found an invalid SETUP.INF on the user's
system. Follow the instructions for S001.
S014
Entry not found in SETUP.INF: [winexec].execstd. Setup
has probably found an invalid SETUP.INF on the user's
system. Follow the instructions for S001.
S015
Entry not found in SETUP.INF: [winexec].execcmd. Setup
has probably found an invalid SETUP.INF on the user's
system. Follow the instructions for S001.
S016
Entry not found in SETUP.INF: [user] section. Setup has
probably found an invalid SETUP.INF on the user's
system. Follow the instructions for S001.
S017
Entry not found in SETUP.INF: [user] section empty.
Setup has probably found an invalid SETUP.INF on the
user's system. Follow the instructions for S001.
S018
Entry not found in SETUP.INF: [user] section corrupt.
Setup has probably found an invalid SETUP.INF on the
user's system. Follow the instructions for S001.
S019
WIN.COM not created. This may be due to missing files, a
bad SETUP.INF or OEMSETUP.INF, lack of disk space, or an
inability to create or modify the WIN.COM file. When you
first install Windows or change display drivers, Setup
creates the file WIN.COM from the file WIN.CNF and
displays the dependent logo files, usually named *.lgo
and *.rle. The logo files are specified in the .INF file
for the chosen display.
Make sure you do not have virus-protection software that
does not allow executables to be modified. Try changing
the display after exiting Windows and running Setup from
the MS-DOS prompt. If you are selecting an original
equipment manufacturer (OEM) display, try one of the
display drivers that are shipped with Windows 3.1 to see
if the OEMSETUP.INF file is not valid or if it specifies
files that do not exist. If selecting a supplied display
driver does not work, make sure the SETUP.INF file is
valid (see error S001 above).
S020
SYSTEM.INI was not correctly updated. This will occur
when attempting to configure Windows with a new device
or for a new system software configuration. The main
reason for this problem occurring is lack of memory or a
corrupt SYSTEM.INI file. It is also possible to get this
error because of a corrupt .INF file. Make sure there is
enough memory and that the SYSTEM.INI file is of a
reasonable size (not much more than 5K) and try the
operation again. Try selecting a different component
(for example, select No Network instead of the network
selected or select VGA instead of the display that is
selected). If this succeeds, copy the SYSTEM.INI file to
a backup disk and try again. If not, the SYSTEM.INI or
SETUP.INF file is probably corrupted.
S021
SYSTEM.INI was not correctly updated. See S020 above.
S022
Setup did not save its state in the SYSTEM.INI file
This is due to either insufficient memory or a corrupt
SYSTEM.INI file.
GUI Mode Setup Error Codes
--------------------------
208
Out of disk space during file copy in VerInstallFile. Because of
the disk space checks that Setup does, this problem should occur
only if you have upgraded over an invalid Windows installation
(that is, files have been deleted manually). Make sure there is
enough disk space and then run Setup again. Also make sure that
VER.DLL does not exist in the WINDOWS directory. It should only be
in the WINDOWS\SYSTEM directory.
209
File in use. This error occurs if some file that needs to be
replaced by Setup is in use or opened by another some other
software. Make sure Setup is the only application running or exit
Windows and run Setup from the MS-DOS prompt.
210
Destination file is write-protected. Type
ATTRIB -r <filename>
at the MS-DOS prompt, where "<filename>" is the indicated file and
run Setup again. This problem may also be caused by virus-
protection software, in which case, this software should be
disabled while running Setup.
211
Buffers allocated for file expansion operations are too small.
This error should never occur. If it does, free up some memory and
run Setup again.
212
Unknown version mismatch happened during attempt to install file.
This problem can be caused by the incorrect version of VER.DLL
running or by corrupt files. Make sure you do not have VER.DLL in
your WINDOWS directory. It should only be in the WINDOWS\SYSTEM
directory.
213
File expansion initialization failed. This problem is probably due
to insufficient memory.
214
Source file is unreadable. This problem is probably due to drive
hardware problems, corrupt files or disks or, if you are setting
up from a network, network problems
Updated: 92/07/02
ms-windows